Safe WASH Recovery Programme · Month 12 · Operational Pressure Rising
In the diagnostic, you made decisions. In the War Room, you will document them. Three PRINCE2 management products are waiting in your tray. Open each tab to review — then enter.
Your live record of every threat and opportunity. You will classify a new risk, rate its probability and impact, assign a response strategy, and flag it for escalation or local management.
REVIEWED · USED IN SLIDE 25Raised when any tolerance is forecast to be breached. You will complete five sections — cause, consequences, options, recommendation, and Business Case impact — before the Project Board meeting.
REVIEWED · USED IN SLIDE 26Your scheduled progress narrative to the Project Board. You will update three sections based on live project data: budget status, risk and issues, and requests for guidance.
REVIEWED · USED IN SLIDE 28Site 4 procurement variance pattern matches previous Somalia WASH audit finding. A new risk requires logging.
+12 days beyond ±7-day tolerance. Exception Report must be raised before the Project Board meeting in 8 days.
Not a score. A trace of six decisions across fourteen days. Where the alignments line up, you are operating on principle. Where they diverge — that is where the learning lives.
Four management products. Fourteen days. One Project Board. Click each card to reveal what it tested.
Logged under pressure. P×I, response strategy, owner, escalation flag.
Five sections under pressure. Cause, consequences, options, recommendation, Business Case.
Updated under pressure. Budget, risks, requests for guidance.
You defended fourteen days of decisions in four questions.
Same judgment the War Room required. No hedging, no guessing — operational decisions in writing.
An adaptive environment, not a course. It calibrates to how you think under pressure — across role, language, and modality.
Role drives scenario context, stakeholder names, PM challenge framing, and the AI's vocabulary detection for your entire session. This is not skin — it is calibration.
Synthesis at L5–L6 requires authentic cognitive context — not translated scaffolding. Switching language switches stakeholder names, regional references, VO track, and AI register. Your decision history is preserved across switches.
Try each one below — the AI begins reading your modality preference silently from this point on.
Stage Gate review for Diourbel WASH Phase 2 is due in 4 days. Exception threshold on cost tolerance has been breached by 8%. Project Board has not been notified.
Community consultation log for Thiès district is incomplete. Procurement cannot proceed without it. Field team is requesting authorisation pathway.
Your Highlight Report is overdue by 72 hours. Project Board confidence indicator has shifted from green to amber.
Questions are genuinely ambiguous. The AI is reading response time, hesitation events, answer revision, and help-seeking — not correctness.
You are 11 weeks into a 16-week project. Cost tolerance band: ±5%. Current variance: +6.8%. Schedule still on track. Highlight Report due tomorrow morning.
No visual hierarchy — all three are equally defensible PM responses. AI follow-up is a question, not a verdict.
Three observed dimensions from 4 decisions and 6 dialogue exchanges. The bars are descriptive, not evaluative.
Plans are made under calm — decisions are made under pressure. Both must be evaluated.
"Community leader is asking to meet. What do we tell them?"
"Why has work not resumed? Board meets in 2 hours. Bring a plan, not a problem."
"We need confirmation that schedule impact is contained."
"When a project faces an unstructured crisis, I believe the PM's first responsibility is to ___."
AI's register shifts — collegial, direct, never evaluative.
You leave with a usable team learning design — not a course completion.